[curious-question] Shouldn't we move this react and react-dom to the devDependencies object so we can still work with this editor in dev mode without accounting for another package in this workspace to bring them? 🤔

@lordrip Shouldn't be the final package, importing @kie-tools-examples/base64png-editor, to provide react in dependencies of devDependencies?

@fantonangeli , yes, the final package (consumer) should definitively provide react. I was referring to another case though.

Let's ignore for a moment that @kie-tools-examples/base64png-editor belongs to this repository, so the package json for it would look like the following:

{
  "name": "@kie-tools-examples/base64png-editor",
  ...
  "dependencies": {},
  "devDependencies": {
    "typescript": "5.0.0"
  },
  "peerDependencies": {
    "react": ">=17.0.2 <19.0.0",
    "react-dom": ">=17.0.2 <19.0.0"
  }
}

Now, performing a yarn install won't bring react to the project, so the project will fail when trying to run it in standalone mode as there's no react dependency in the node_modules.

Now, this repository is slightly different as it's very likely that some other package is bringing react to the node_modules, hence making it work, but if by any chance I bootstrap just the @kie-tools-examples/base64png-editor maybe it will fail, as some dependencies of other packages won't be brought?

I'm not familiar with how pnpm works in terms of bootstraping packages and whether if it will download dependencies for unresolved packages, but if it does, then I think we're good, otherwise, 💥

Maybe 💥 is a bit too dramatic